home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000193_icon-group-sender _Sun Jul 3 19:57:20 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-08-19
|
1KB
Received: by cheltenham.cs.arizona.edu; Mon, 4 Jul 1994 10:50:58 MST
Date: Sun, 3 Jul 94 19:57:20 CDT
From: jeffery@runner.jpl.utsa.edu (Clinton L. Jeffery)
Message-Id: <9407040057.AA15563@runner.utsa.edu>
To: rprice@reunion.umd.edu
Cc: icon-group@cs.arizona.edu
In-Reply-To: <2v4pqi$a16@umd5.umd.edu> (agate!howland.reston.ans.net!europa.eng.gtefsd.com!news.umbc.edu!haven.umd.edu!umd5.umd.edu!usenet@ucbvax.Berkeley.EDU)
Subject: Re: Icon installation on NeXT 3.2
Content-Length: 577
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
[Rod Price gets warning messages when he runs Icon compiler binaries
for Next 2.1 on his Next 3.2 platform, and asks:]
How do I fix this?
These are a first guess at your options:
(1) Use the Icon interpreter instead of the Icon compiler. Not to be glib,
but the interpreter compiles way faster, and its executables run only a
moderate amount slower (~3 times), than the Icon compiler.
(2) Get the Icon sources and build Icon from scratch on your platform.
Clint Jeffery
jeffery@ringer.cs.utsa.edu, cjeffery@cs.arizona.edu
The University of Texas at San Antonio